Label switched path OAM wrapper

ABSTRACT

Methods and devices for logically segmenting an LSP so that OAM DTUs may be used to determine the performance and/or the status of LSP segments. To segment a previously determined LSP, a dedicated subpath (a logical LSP) within that predetermined LSP is defined between two LSRs that are capable of processing OAM DTUs. The source node (source LSR) establishes a logical LSP between itself and the destination node (destination LSR) using an LDP. In doing this, the logical LSP traverses a specific path and transits through specific nodes in that path. The source node then transmits an OAM DTU or any other specialized DTU to the destination node using a label specifically associated with the logical LSP that was established. The characteristic of the specific path traversed by the logical LSP can thus be determined by when, how, and if the specialized DTU is received by the destination node.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is in continuation of U.S. patent application Ser. No.10/032,014 filed Dec. 31, 2001.

FIELD OF THE INVENTION

The invention relates to communications networks and, more particularly,to methods and devices for determining the performance of networksegments in a Multi-Protocol Label Switched (MPLS) network.

BACKGROUND TO THE INVENTION

Today's increasing use of and reliance on communications networks hasled to the development of new standards and protocol that provide morereliable and efficient network services to consumers.

A standard that is still developing is MPLS (Multi-Protocol LabelSwitching). This emerging standard allows packets or any datatransmission units (DTUs) to be routed in the MPLS network based simplyon a label that the DTU is carrying. This process facilitates thecomplexity of route lookups that are based on a destination IP (InternetProtocol) address. Thus, a DTU (Data Transmission Unit) arriving at arouter is forwarded to another router based merely on the a DTU's label.At the next router, the label of the DTU may be replaced or added to forthe next “hop” in the DTU's travel towards its ultimate destination.While the MPLS standard promises great benefits, very few methods havebeen developed for fault detection/management of an MPLS network.

One solution to the above need has been suggested by ITU-T Y.1711. Inthis document, discussed is the use of a special Operation AndMaintenance (OAM) packet that can be used to determine the performanceof an MPLS network. An unused reserved MPLS label value is used at thebottom of the label stack of OAM packets to delineate OAM packets fortransport between Label Switch Path (LSP) ingress and egress points.This approach, unfortunately, only allows for performance determinationbetween these ingress and egress points. The performance of networksegments between these ingress and egress points is not possible noreven considered in the above proposal. Furthermore, the use of aspecific MPLS label value for OAM packets leads to increased overheadcosts for this proposal.

By way of explanation, it should be noted that an LSP is a specific datatraffic path in an MPLS network. Such LSPs are provided for by LDPs(Label Distribution Protocols) that establish these paths and reservesthe necessary resources on the nodes in the path to meet predefinedservice requirements of the data path. An LSP is analogous to the routethat a packet or DTU is tasked to follow in being transmitted from aningress (entry) LSP node to an egress (exit) LSP node. LSPs areestablished from the egress LSP node to the ingress LSP node. As such,the egress LSP node uses LDP to distribute the relevant labels to therelevant nodes. Once a DTU arrives at the ingress LSP node, the DTU isthus forwarded to the egress LSP node based on the forwarding decisionsdictated by the distributed labels.

An LDP is a specification that allows a label switch router (LSR) todistribute labels to its LDP peers. In MPLS, since DTUs are routed basedon the labels carried by the DTUs, the routers (LSR) must know where toroute the DTUs based on the labels carried by the DTU. Thus, if an LSRassigns a label A to a class of DTUs, that LSR must notify the otherLSRs of the meaning of that label A (i.e. what to do or how to processor route a DTU with label A). This is accomplished by using an LDP.Since a set of labels from the ingress LSR (entry router) to the egressLSR (exit router) in an MPLS network defines a Label Switched Path(LSP), LDPs help in establishing an LSP by using a set of procedures todistribute the labels among the LSP peers (i.e. the ingress LSP and theegress LSPs are peers in that they communicate with each other at thesame level—they can change what each has done).

From the above discussion, any solution to the above performancedetermination problem should ideally make use of the existinginfrastructure that adheres to the MPLS standard. Such a solution wouldnot require increased logic to be implemented and should allow forsegmentation of LSPs in terms of performance and fault isolation.

It should be noted that the term data transmission unit (DTU) will beused in a generic sense throughout this document to mean units throughwhich digital data is transmitted from one point in a network toanother. Thus, such units may take the form of packets, cells, frames,or any other unit as long as digital data is encapsulated within theunit. Thus, the term DTU is applicable to any and all packets and framesthat implement specific protocols, standards or transmission schemes. Itshould also be noted that the term digital data will be used throughoutthis document to encompass all manner of voice, multimedia content,video, binary data or any other form of data or information that hasbeen digitized and that is transmitted from one point in a network toanother as a payload of a data transmission unit.

SUMMARY OF THE INVENTION

The present invention seeks to provide methods for logically segmentingan LSP so that OAM DTUs may be used to determine the performance and/orthe status of LSP segments. To segment a previously determined LSP, adedicated subpath (a logical LSP) within that predetermined LSP isdefined between two LSRs that are capable of processing OAM DTUs. Thesource node (source LSR) establishes a logical LSP between itself andthe destination node (destination LSR) using an LDP. In doing this, thelogical LSP traverses a specific path and transits through specificnodes in that path. The destination node then transmits an OAM DTU orany other specialized DTU to the source node using a label specificallyassociated with the logical LSP that was established. The characteristicof the specific path traversed by the logical LSP can thus be determinedby when, how, and if the specialized DTU is received by the destinationnode.

In a first aspect the present invention provides a method of routing aspecial type of a data transmission unit between a source node and adestination node in a network that only allows unidirectional routing,both the source node and the destination node being capable ofprocessing the special type of data transmission unit, the methodcomprising:

-   -   a) selecting intermediate nodes to be traversed transmitted by        the DTU when transmitted from the source node to the destination        node;    -   b) designating the intermediate nodes selected in step a) as        being in a specific path of nodes between the source node and        the destination node;    -   c) creating the DTU at the source node; and    -   d) transmitting the DTU from the source node to the destination        node along the specific path of nodes.

In a second aspect the present invention provides a method of segmentinga predefined path through a network that only allows unidirectionaltransmission, the method comprising:

-   -   a) determining which nodes on the network are on the predefined        path;    -   b) defining segment nodes that define beginning and ending nodes        for a network segment; and    -   c) configuring a network segment between beginning and ending        nodes by instructing intervening nodes on how to forward data        transmission units configured for that network segment.

In a third aspect the present invention provides a method of determininga performance of a network path, the method comprising:

-   -   a) dividing the network path into segments, each segment having        a source node defining a beginning of the segment and a        destination node defining an ending of the segment;    -   b) transmitting a specialized data transmission unit from the        source node to the destination node;    -   c) receiving the specialized data transmission unit at the        destination node; and    -   d) calculating the performance of the segment based on data        contained in the specialized data transmission unit.

In a fourth aspect the present invention provides a method ofdetermining a performance of a network path, the method comprising:

-   -   a) dividing the network path into segments, each segment having        a source node defining a beginning of the segment and a        destination node defining an ending of the segment;    -   b) transmitting a specialized data transmission unit from the        source node to the destination node; and    -   c) determining if there is a fault on the segment based on        whether the specialized data transmission unit is received by        the destination node within a given amount of time.

In a fifth aspect the present invention provides a network router forrouting data transmission units (DTUs) in a domain which only allowsunidirectional flow, the router including:

-   -   a receiving module for receiving DTUs;    -   a transmitting module for transmitting DTUs;    -   a switch core module placed between the receiving module and the        transmitting module for routing DTUs between the receiving and        the transmitting modules; and    -   a diagnostic module for determining a performance of a network        path of the domain, the diagnostic module being for processing        specialized DTUs received by the receiving module and for        creating specialized DTUs to be transmitted by the transmitting        module,        wherein the router executes computer readable and computer        executable instructions for implementing a method for        determining the performance of the network path, the method        including:    -   a) if the network router is a source node for the network path,        transmitting the specialized DTUs to a destination node; and    -   b) if the network router is a destination node for the network        path, receiving the specialized DTUs and performing an action        chosen from the group consisting of:        -   b1) calculating the performance of the network path based on            data contained in the specialized DTU; and        -   b2) determining if there is a fault on the network path            based on whether a specialized DTU is received within a            given amount of time.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the invention may be obtained by reading thedetailed description of the invention below, in conjunction with thefollowing drawings, in which:

FIG. 1 is a block diagram of an MPLS network using label switchedrouters;

FIG. 1A is a block diagram illustrating the logical adjacencies allowedby OAM wrappers;

FIG. 2 is a flowchart illustrating the steps in a method according toone aspect of the invention;

FIG. 3 is a diagram of the fields in an MPLS DTU which may be used fortransporting OAM data between LSRs; and

FIG. 4 is a block diagram of the components a Label Switched Router(LSR) which may be used to implement one aspect of the invention.

DETAILED DESCRIPTION

For this document, the term “OAM-capable” will be understood to meancapable of processing OAM DTUs or some other specialized DTU used formaintenance and/or performance determination purposes. Processing suchDTUs may involve producing such DTUs, determining network segmentperformance from the DTUs and determining network or network segmentfaults by the receipt or non-receipt of such DTUs. Based on the above, a“non-OAM capable” node will thus be nodes that are unable to processsuch specialized DTUs.

Referring to FIG. 1, a schematic block diagram of an MPLS network 10 isillustrated. A first OAM capable LSR 20 (LSR0) is coupled to a node 30.The node 30 is coupled to another node 40 which, in turn, is coupled toa second OAM capable LSR 50 (LSR5). At another end of LSR 20, a non OAMcapable LSR 60 (LSR1) is coupled to LSR 20 through two intervening nodes70, 80. This non-OAM capable LSR 60 is also coupled to another OAMcapable LSR 90 (LSR6) with no intervening nodes in between. At anotherport of LSR 60, another non-OAM capable LSR 100 (LSR4) is coupled to LSR60 with three intervening nodes 110, 120, 130 in between. This LSR 100is coupled, in turn, to LSR 90 with three intervening nodes 140, 150,160 in between. At yet another port of LSR 60, this LSR 60 is coupled toan OAM capable LSR 170 (LSR2) through one intervening node 180. BetweenLSR 170 and an OAM capable LSR 190 (LSR3) are three intervening nodes200, 210, 220. The LSR 190 is also coupled to LSR 100 at another of itsports.

It should be noted that intervening nodes 30, 40, 70, 80, 180, 140, 150,160, 110, 120, 130, 200, 210, 220 are not of interest and are merelynetwork nodes that are non-OAM capable. For non-OAM capable nodes andLSRs OAM is transparent to these nodes and LSRs. These nodes areprovided as illustration that other nodes may be present between therelevant LSRs.

With the network 10 as illustrated in FIG. 1, previously suggestedsolutions to the problem outlined above would only be capable ofdetermining end-to-end performance between an ingress LSR and an egressLSR of an LSP. If the LSP was a path from LSR0 to LSR3, with the LSPpassing through LSR1 and LSR2, then only the performance for the wholepath can be found. The isolation of any faults in that path is notpossible. Thus, if the node 180 were to fail, then a user would onlyknow that the LSP between LSR0 and LSR3 has failed and that user wouldnot be able to isolate the problem to any specific portion of the path.

Segmentation of the MPLS network is achieved by configuring logical LSPswithin a given LSP. If the example given above of an LSP with LSR0 as aningress LSR and LSR3 as an egress LSR is taken, logical subsidiary LSPscan be created within this LSP. Since this LSP passes through an OAMcapable LSR, LSR2, this LSR can be the breakpoint within the larger LSP.Thus, a subsidiary logical LSP between LSR0 and LSR2 can be created andanother subsidiary logical LSP segment between LSR2 and LSR3 can becreated.

By setting up a local LSP segment between LSR0 and LSR2, any faults inthat network segment can therefore be isolated. Similarly, if there is afault between LSR2 and LSR3, then the fault can be isolated to thatsegment. If the MPLS network cannot be segmented between the ingressLSR0 and the egress LSR3, then any fault between these two LSRs cannotbe localized. If the MPLS network can be segmented, then by checkingeach segment the problem can be isolated.

To segment the LSP between LSR0 and LSR3, the source node, in this caseLSR0, would create an LSP segment between itself, LSR0, and the closestOAM capable LSR. In this case the nearest OAM capable LSR would be LSR2.An LSP segment between LSR0 and LSR1 would not be of any use given thatLSR1 cannot process the OAM or specialized DTU. To provision this firstLSP segment, LSR0 would use the LDP to notify all the nodes betweenitself and the destination node that a new LSP segment has beenestablished and that any DTUs carrying the label that is assigned to thenew LSP segment must be processed accordingly. With the first subsidiaryLSP established, a second LSP segment can be created between LSR2 andLSR3. This second LSP segment would be useful as it is between OAMcapable LSRs. It should be clear that these LSP segments are beingdefined within an LSP that has been previously established. The LSPsegments are denoted as an attribute of this previously established LSP.The LSP segments are defined when the original LSP is defined. Ineffect, an “OAM wrapper” is established for each possible segment as anattribute of that LSP. Thus, if a path for an LSP changes, the newlabels distributed to setup the new path will carry with it the OAMwrapper attribute of the LSP. LSP segments are defined and for each LSPsegment delimited by OAM capable LSRs or non-OAM LSP segments (e.g. LSR1in FIG. 1), an OAM wrapper can be established. Thus, in FIG. 1, the LSPsegment defined between OAM capable LSRs, LSR2 and LSR3 can have an OAMwrapper associated with it. Similarly, the LSP segment between LSR0 andLSR2 can have its own OAM wrapper associated with it.

To establish the second LSP segment the source node, either of LSR2 orLSR3, can initiate the process by provisioning for the LSP segment andusing LDP to notify the nodes between itself and the destination LSR howDTUs with the label for this second LSP segment will be processed. Oncethese two LSP segments are established, it should be clear that anyproblems in the original LSP between LSR0 and LSR3 can be localized toeither of the two LSP segments. If there is a problem in the originalLSP then this problem may be localized by using the LSP segments topinpoint the problem. The first LSP segment between LSR0 and LSR2 can beactivated and LSR0 can send a specialized fault detection DTU or aregular OAM DTU to LSR2 to determine if the fault is within that segmentof the original LSP. Simultaneously, the second LSP segment between LSR2and LSR3 can be examined by having the destination node send a similarfault detection or OAM DTU to the destination LSR to determine if thefault is within that segment. By this process of segmentation andelimination, faults along a previously determined LSP can be localizedand isolated.

Again taking FIG. 1 as an example, the OAM wrappers that can beestablished are as follows:

-   OAM wrapper A:    -   between LSR0 (ingress) and LSR5 (egress)-   OAM wrapper B:    -   between LSR6 (ingress) and LSR3 (egress)-   OAM wrapper C:    -   between LSR1 (ingress) and LSR2 (egress)-   OAM wrapper D:    -   between LSR2 (ingress) and LSR3 (egress)

The OAM wrapper establishes logical adjacencies between LSRs that areequipped with OAM capabilities for performance measurement and faultisolation. The ingress and egress points are set out clearly in the OAMwrapper setup to account for the unidirectional nature of MPLS. Thelogical links or adjacencies between the OAM capable LSRs areillustrated in FIG. 1A. As can be seen in FIG. 1A, LSR0 is logicallyadjacent to LSR5, LSR2, LSR3, and LSR6 for OAM purposes. Furthermore,LSR6 is logically adjacent to LSR3 and LSR2 is also logically adjacentto LSR3 for OAM purposes. The intervening nodes between these LSRs arenon-OAM capable and are thus transparent to the OAM DTUs and are notincluded in FIG. 1A. Also, since LSR1 and LSR4 are non-OAM capable,these are also transparent to OAM and OAM DTUs and are not included inFIG. 1A.

As part of the establishment of a LSP segment, at least one label has tobe assigned to the LSP segment. This involves the establishing node,usually the source LSR, choosing a label in the LSP segment. Once thislabel is chosen, it is then assigned to the LSP segment. Once assigned,the label can then be inserted into the OAM DTU. It should be noted thatthis assignment is communicated to the other nodes using LDP. This waythe other nodes are notified of the new label and of the new LSPsegment.

To ensure that a LSP segment will traverse a specific path through thenetwork, the LSP segment can be configured to proceed along a specificpath. As an example, if an LSP between LSR0 and LSR3 is configured totravel any path between LSR0 and LSR3 then multiple possibilities existfor this path. For example a DTU on that LSP, which we can label as theprimary LSP, can take the path from LSR0 to LSR1, then to LSR6, LSR4,and finally, to LSR3. Or, that same DTU may take the path from LSR0 toLSR1, then to LSR2, and finally to LSR3. As a third path the DTU couldtravel from LSR0, in to LSR1, LSR4, and, finally, to LSR3. Clearly, toperform fault management and/or performance determination and managementon the primary LSP between LSR0 and LSR3 in this configuration can bedifficult. However, if LSPs segments are created between the OAM capableLSRs in this configuration, then both fault management and performancedetermination is simplified. As an example, an LSP subsidiary can becreated between LSR0 and LSR6 passing through LSR1. Similarly, a LSPsegment can be created between LSR6 and LSR3 passing through LSR4. Also,an LSP segment can be created between LSR0 and LSR3 passing through LSR1and LSR4. To ensure that the correct path is being created and examined,the LSP between the OAM capable LSRs can be created to follow a veryspecific path. As an example, an LSP segment between LSR6 and LSR3 canbe created by using LDP to notify all the nodes that a DTU passingthrough this LSP must pass through node 140, 150, 160 and LSR4.Similarly, if an LSP segment between LSR0 and LSR3 is to be created totest the links between LSR1 and LSR4, then this LSP segment should beconfigured such that any DTU on this LSP must pass through nodes 110,120, and 130.

Concerning the OAM DTU that may be transmitted from a source node to adestination node, this OAM DTU can be created in a well known manner anddesigned according to a user's specific need. To further clarify itshould be noted that a source node and a destination node are ideallyOAM capable LSRs. An LSR is a node that can route traffic based on theirlabels.

The OAM DTU can be as simple as a DTU that has a date and time stamp ofwhen the DTU was transmitted from a source node. This OAM DTU, whenreceived by the destination node, is processed by merely reading thedate and time stamp and comparing that with the date and time at whichthe OAM DTU was received at the destination node. By doing thiscomparison, the transit time from the source node to the destinationnode can be determined as long as, of course, the clocks in the sourcenode and the destination node are substantially synchronized. For faultisolation, the source node can send a confirmation OAM DTU to adestination node. The faults on the LSP segment can be found if theconfirmation DTU is not received by the destination node. This faultdetection can be continuously carried out with the source node of theLSP segment sending a confirmation OAM DTU to the multiple destinationnodes at a specified rate. The destination node can, based on theaverage transit time for an OAM DTU, determine if the source nodetransmitting the confirmation OAM DTUs is still communicating. If adestination node does not receive a confirmation OAM DTU within apredetermined amount of time after the previous confirmation OAM DTU,then the destination node may decide to issue a warning that a fault onthe LSP segment of the primary LSP is present. This will therefore allowusers and/or network management software to look further into thematter.

FIG. 2 is a flow chart illustrating the steps taken in the processoutlined above. The first step is step 230. This step chooses theprimary LSP to be segmented. Step 240 determines the path in the primaryLSP for an LSP segment. As an example, in FIG. 1, if the primary LSP isfrom LSR0 to LSR3 then the second step would be to determine whether theLSP segment passes through LSR0, LSR1, and LSR2, through LSR0, LSR1,LSR4, or through LSR0, LSR1, LSR6 and LSR4 and, finally, LSR 3. Afterthis, the next step (step 250) is that of provisioning or allowing foran LSP segment to be established. This step involves determining thelabel to be assigned to the LSP segment and allocating resources forthis label to be assigned. Step 260 involves notifying the other nodesand LSRs in the MPLS network about the LSP segment being created. Thisnotification is normally done using LDP. This notification notifies thenodes in the path of the LSP segment about how packets having the labelassigned to that LSP segment is to be forwarded and or processed.

Once the LSP segment has been setup by assigning the label for that LSPand by notifying the nodes in the LSP segment, the source node or thesource LSR can now create the OAM DTU and/or the specialized DTU fortransmission to the destination node (step 265). Step 270 is then thatof actually transmitting the OAM DTU from the source node to thedestination node along the LSP segment. Step 280 receives the OAM DTU atthe destination node. This step assumes that the OAM DTU arrives at thedestination node and that there is no fault along the LSP segment.Finally, step 290 is that of processing the OAM DTU at the destinationnode to determine the performance of the LSP segment and/or to determinethe configuration of the LSP segment.

Referring to FIG. 3, a possible format for MPLS DTUs is illustrated. Ascan be seen, a PPP (Point-to-Point Protocol) field 300 provides for datarelated to the PPP protocol while a transport label field 310 and aservice label field 320 allows the DTU to be used in an MPLS domain. Thecontents of the transport label field 310 determines the routing of theDTU while the contents of the service label field 320 determines theservice or processing provided to the DTU. The OAM label field 325carries an OAM label which signals to the destination node that it is anOAM DTU. The inclusion of this field is in accordance with the documentITU-T.1711. The payload 330 contains any data to be transported whilethe CRC field 340 provides error correction for the DTU. If the DTU isto be used as an OAM DTU, then any data which may be needed by an OAMDTU may be placed in the payload field 330. The OAM wrapper discussedabove would be evidenced by an OAM label in the OAM label field 325. AnOAM capable LSR which processes the DTU would recognize the specializedOAM label and process the DTU accordingly. Non-OAM capable nodes (suchas nodes 140, 150 in FIG. 1) would not recognize the specialized OAMlabel and would merely forward the OAM DTU to the next node.

Referring to FIG. 4, illustrated is a block diagram of an OAM capableMPLS router (LSR) which may use the invention.

As can be seen in FIG. 4, the router 400 has three main components: aninput module 410, a switch core 420, and an output module 430. The inputmodule 410 receives DTUs from upstream nodes. The switch core 420 thenswitches these DTUs to the proper egress ports on the output module 430.Prior to forwarding the received DTU, the LSR processes the DTU. If theDTU is an OAM DTU, then the LSR may respond to the OAM DTU to indicatethat the OAM DTU has arrived. It is at this point that the routerimplements the invention as explained above. The implementation can becarried out by the output module 430 prior to transmitting the OAM DTUsacross the MPLS domain. Alternatively, an extra OAM module 440 may beprovided between the output module that would process the OAM DTUs andensure that such OAM DTUs are properly processed, sent or responded to.Furthermore, such an OAM module would ensure that the MPLS transport ofthe OAM DTUs is properly provisioned. To this end, the OAM module wouldhandle the signalling and LDP execution to implement the invention. TheOAM module would therefore perform the processing, signalling,encapsulation, and service label allocation that are outlined above. Itshould be clear that the above description for FIG. 4 applies to asource node for an OAM DTU. This source node LSR would originate andtransmit the OAM DTU to a destination LSR that would receive the OAMDTU.

If the OAM capable LSR is a destination node, the parts of thisdestination node are the same as those illustrated in FIG. 4 except thatthe MPLS module would be placed such that the receive module 410 isbetween the MPLS module 440 and the switch core 420. Such a destinationnode would receive OAM DTUs and, prior to processing them as regularDTUs, would process them as OAM DTUs.

Embodiments of the invention may be implemented in any conventionalcomputer programming language. For example, preferred embodiments may beimplemented in a procedural programming language (e.g. “C”) or an objectoriented language (e.g. “C++”). Alternative embodiments of the inventionmay be implemented as pre-programmed hardware elements, other relatedcomponents, or as a combination of hardware and software components.

Embodiments can be implemented as a computer program product for usewith a computer system. Such implementation may include a series ofcomputer instructions fixed either on a tangible medium, such as acomputer readable medium (e.g., a diskette, CD-ROM, ROM, or fixed disk)or transmittable to a computer system, via a modem or other interfacedevice, such as a communications adapter connected to a network over amedium. The medium may be either a tangible medium (e.g., optical orelectrical communications lines) or a medium implemented with wirelesstechniques (e.g., microwave, infrared or other transmission techniques).The series of computer instructions embodies all or part of thefunctionality previously described herein. Those skilled in the artshould appreciate that such computer instructions can be written in anumber of programming languages for use with many computer architecturesor operating systems. Furthermore, such instructions may be stored inany memory device, such as semiconductor, magnetic, optical or othermemory devices, and may be transmitted using any communicationstechnology, such as optical, infrared, microwave, or other transmissiontechnologies. It is expected that such a computer program product may bedistributed as a removable medium with accompanying printed orelectronic documentation (e.g., shrink wrapped software), preloaded witha computer system (e.g., on system ROM or fixed disk), or distributedfrom a server over the network (e.g., the Internet or World Wide Web).Of course, some embodiment of the invention may be implemented as acombination of both software (e.g. a computer program product) andhardware. Still other embodiments of the invention may be implemented asentirely hardware, or entirely software (e.g. a computer programproduct).

1. A method of routing an operation and maintenance (OAM) datatransmission unit (DTU) in a multi-protocol label switched (MPLS)network, between a source node and a destination node, the MPLS networkhaving a label switched path (LSP), the source node and the destinationnode being capable of processing OAM DTUs, the source node and thedestination node having intermediate nodes disposed therebetween, theintermediate nodes including OAM nodes, the OAM nodes being capable ofprocessing OAM DTUs, the method comprising: a) defining segments of theLSP path in accordance with the source node, the destination node andthe OAM nodes; b) defining an OAM label for the DTU in accordance withthe segments; c) providing to the intermediate nodes instructions on atleast one of how to forward the OAM DTU and how to process the OAM DTU;and d) binding the OAM label to the OAM DTU in an OAM label field, theOAM DTU including an MPLS label in an MPLS label field, the OAM labelfield being distinct from the MPLS label field.
 2. The method as claimedin claim 1 wherein the instructions include instructions on how todetermine a performance of a segment.
 3. A method as in claim 1 furthercomprising reserving resources in the OAM nodes in accordance with whichthe segments have been defined.
 4. The method as claimed in claim 1wherein providing to the intermediate nodes instructions is effectedwith a label distribution protocol.
 5. The method as claimed in claim 1wherein the OAM nodes include a label switched router.
 6. The method asclaimed in claim 5 wherein the instructions include routinginstructions.